home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-02
/
autodox2.zip
/
MANUAL.DOC
< prev
next >
Wrap
Text File
|
1992-07-18
|
8KB
|
301 lines
AutoDOX v2.00
Copyright (c) 1992, TDM Software - ALL RIGHTS RESERVED
Designed & Written by Chris Hettinger
Page 1
AutoDox v2.00 Copyright (c) 1992 TDM Software - ALL RIGHTS RESERVED
DISCLAIMER
Users of AutoDOX must accept this disclaimer of warranty:
"AutoDOX is supplied as is. The author disclaims all warranties,
expressed or implied, including, without limitation, the warranties
of merchantability and of fitness for any purpose. The author
assumes no liability for damages, direct or consequential, which
may result from the use of AutoDOX."
SHAREWARE AGREEMENT
AutoDOX is a "shareware program" and is initially provided at no
charge. Feel free to share it with your friends, but please do
not give it away altered or as part of another system. Anyone
distributing AutoDOX for any kind of remuneration must first
contact TDM at the address listed below for authorization.
This authorization will be automatically granted to distributors
recognized by the (ASP) as adhering to its guidelines for
shareware distributors, and such distributors may begin offering
AutoDOX immediately; however, TDM must still be advised so that
the distributor can be kept up-to-date with the latest version of
AutoDOX.
If you like AutoDox and would like to remain using it, send the
enclosed registration form (REGISTER.FRM), and $25 to the following
address:
TDM Software c/o Chris Hettinger
3054 Pritchard Hall - East
Va. Tech
Blacksburg, VA. 24060-0023
Fully commented source code for AutoDOX is available for $50.
This includes a royalty free license agreement and one year of
free upgrades.
RELEASE HISTORY
1.0 March 1992 Initial release, aimed at doing the busy work
for my CompSci class at Tech
2.0 July 1992 Second release, a more complete utility. Now
allows for input of procedure headers, and
compiles lists of procedures.
ACKNOWLEDGMENTS
* Turbo Pascal is a registered trademark of Borland International
* MS-DOS is a registered trademark of Microsoft Corporation
* All other programs are (c) and/or (tm) by their respective
author unless otherwise noted
Page 2
AutoDox v2.00 Copyright (c) 1992 TDM Software - ALL RIGHTS RESERVED
WHAT IS AUTODOX?
AutoDox is a tool to assist you in the documentation of pascal source
code. AutoDox can create procedure/function headers, or compile a list of
procedures in a given file. After using AutoDOX, I believe you'll find it
as useful as I have.
AutoDOX was originally written to defeat the menial commenting
tasks required by my computer science class. Therefore, its main goal was
to save me time. AutoDOX works best on a program that has a minimal
quantity of comments already coded. It was meant to run on a file with
next to no comments, for those of us who like to write the whole program,
and document it when it is finished.
The AutoDOX code is structured to best fit my programming style.
Since there is no way to create a program that would fit everyones needs,
I didn't try. It is, however, quite flexible, and the programming
'restrictions' are minor, and will NOT impose a large effort on the
programmer's effort. The 'restrictions' are listed on the next page.
Page 3
AutoDox v2.00 Copyright (c) 1992 TDM Software - ALL RIGHTS RESERVED
USING AUTODOX. 'Code Restrictions'
Maybe restrictions is a harsh word. AutoDOX will run on any code,
but may give undesired results if the following rules are not adhered to.
So if your unsure if your code will work, give it a try. It may just
save you some time.
Here are the restrictions --
1. The following words must be the first on their line, no commenting
may appear before them:
UNIT, PROGRAM,
FUNCTION, PROCEDURE
Example:
Program TEST;
Bad Example:
(* This is my program *) Program Test;
2. No comments should appear after a procedure header (on the same line),
or inside the passed parameter if you use the (* *) delimters. When
a parameter list spans more than one line, AutoDOX checks for the ')'
on the following lines to find the end of the field. Inline comments
using (* *) will confuse it. The second to last character at the end
of the field must be a ')'.
Example:
Procedure TEST(var A: integer; {This is ok}
var B: real);
^
This must be here.
No comments after it.
Bad Example:
Procedure TEST(var A: integer; (* This is bad *)
var B: real); (* Do not do it *)
And thats about it. Not very restricting as far as I'm concerned. And
the time you save is well worth the change.
Page 4
AutoDox v2.00 Copyright (c) 1992 TDM Software - ALL RIGHTS RESERVED
USING AUTODOX. 'Documenting code, the specifics'
AutoDOX is mostly self-explanatory. The only part that could cause
confusion is entering the comment field.
When you choose to document a file, a screen with 15 lines appears.
What you enter will be tagged before every procedure/function in the
file you are documenting.
There are two special commands that AutoDOX recognizes. They must be
entered alone on a line.
1> &E
This command shortens the length of the comment block. That way
if you don't need 15 lines, AutoDOX will stop after it hits &E.
2> &P
This command enters the procedure/function name that is being
documented. It copies the procedure header into the comment.
It will not use any of your remaining 14 lines, no matter how
many lines the header spans.
TRYING AUTODOX.
Since AutoDOX asks you for the output filename, none of your files can be
overwritten. So you can try it out right away without endangering your
files, or, for the nervous, ...
A sample pascal file is included with this program. It is called
sample.pas. Try using AutoDOX on it and see the results before trying it
on your source code if you do not trust the program.
Don't forget to register your copy today.
Page 5
AutoDox v2.00 Copyright (c) 1992 TDM Software - ALL RIGHTS RESERVED